Skip to content

feat: Add streaming notification stubs for standalone mode - #642

Closed
kalyanpullela wants to merge 1 commit into
openconfig:mainfrom
kalyanpullela:standalone-stubs
Closed

feat: Add streaming notification stubs for standalone mode#642
kalyanpullela wants to merge 1 commit into
openconfig:mainfrom
kalyanpullela:standalone-stubs

Conversation

@kalyanpullela

Copy link
Copy Markdown

Add stub implementations for 9 streaming notification methods:

  • SwitchStateChangeNotification
  • SwitchShutdownRequestNotification
  • FdbEventNotification
  • PortStateChangeNotification
  • PacketEventNotification
  • QueuePfcDeadlockNotification
  • BfdSessionStateChangeNotification
  • TamEventNotification
  • IpsecSaStatusChangeNotification

All return UNIMPLEMENTED as streaming is not supported in standalone mode.

Add stub implementations for 9 streaming notification methods:
- SwitchStateChangeNotification
- SwitchShutdownRequestNotification
- FdbEventNotification
- PortStateChangeNotification
- PacketEventNotification
- QueuePfcDeadlockNotification
- BfdSessionStateChangeNotification
- TamEventNotification
- IpsecSaStatusChangeNotification

All return UNIMPLEMENTED as streaming is not supported in standalone mode.
@kalyanpullela
kalyanpullela requested a review from a team as a code owner January 29, 2026 01:05
@sonikajindal

Copy link
Copy Markdown
Contributor

/gcbrun

@sonikajindal

Copy link
Copy Markdown
Contributor

Hi Kalyan, Did you use this saiserver for any testing?

@kalyanpullela

Copy link
Copy Markdown
Author

Hi Kalyan, Did you use this saiserver for any testing?

Hi Sonika, yes this was used to bypass an error that was caused about 7 seconds after RemoveSwitch was completed.
pure virtual method called → terminate called without an active exception → SIGABRT

@sonikajindal

Copy link
Copy Markdown
Contributor

Hi Kalyan, Did you use this saiserver for any testing?

Hi Sonika, yes this was used to bypass an error that was caused about 7 seconds after RemoveSwitch was completed. pure virtual method called → terminate called without an active exception → SIGABRT

Is this a reply to: https://github.com/openconfig/lemming/pull/641/changes#r2743016059 ?

@kalyanpullela

Copy link
Copy Markdown
Author

pure virtual method called

Hi Kalyan, Did you use this saiserver for any testing?

Hi Sonika, yes this was used to bypass an error that was caused about 7 seconds after RemoveSwitch was completed. pure virtual method called → terminate called without an active exception → SIGABRT

Is this a reply to: https://github.com/openconfig/lemming/pull/641/changes#r2743016059 ?

Actually, I just went back and double checked the work. PR 641 is a mistake. But this pr is required to ensure that I don't run into issues during remove switch.

@sonikajindal

Copy link
Copy Markdown
Contributor

pure virtual method called

Hi Kalyan, Did you use this saiserver for any testing?

Hi Sonika, yes this was used to bypass an error that was caused about 7 seconds after RemoveSwitch was completed. pure virtual method called → terminate called without an active exception → SIGABRT

Is this a reply to: https://github.com/openconfig/lemming/pull/641/changes#r2743016059 ?

Actually, I just went back and double checked the work. PR 641 is a mistake. But this pr is required to ensure that I don't run into issues during remove switch.

AFAIK, this standalone cc saiserver is not used in AlpineVS image (libsaigrpc uses https://github.com/openconfig/lemming/tree/main/dataplane/standalone/sai) or in Lucius (it uses the go server: https://github.com/openconfig/lemming/tree/main/dataplane/saiserver). Thats why I am wondering how did you use this standalone mode?

@kalyanpullela

Copy link
Copy Markdown
Author

pure virtual method called

Hi Kalyan, Did you use this saiserver for any testing?

Hi Sonika, yes this was used to bypass an error that was caused about 7 seconds after RemoveSwitch was completed. pure virtual method called → terminate called without an active exception → SIGABRT

Is this a reply to: https://github.com/openconfig/lemming/pull/641/changes#r2743016059 ?

Actually, I just went back and double checked the work. PR 641 is a mistake. But this pr is required to ensure that I don't run into issues during remove switch.

AFAIK, this standalone cc saiserver is not used in AlpineVS image (libsaigrpc uses https://github.com/openconfig/lemming/tree/main/dataplane/standalone/sai) or in Lucius (it uses the go server: https://github.com/openconfig/lemming/tree/main/dataplane/saiserver). Thats why I am wondering how did you use this standalone mode?

Oh that makes sense, the standalone saiserver isn't brought up at all. I think while looking for causes of fault for RemoveSwitch issue, I might have made modifications to this file.
I'll close this pr as it doesn't affect the operation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants